Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bd197d591c5242ac7ac53da6b95cccdedcef9e518c355ebaf88bb129bf5feff9

Tx prefix hash: c5a16014429c823b94c66ce4dfa07320f7838326025aed1b8bd1bfdcb2c54fac
Tx public key: 752b2e03ebef0aa43ce53a2c3151c5614b0993a115c9cc6ad4cdf246bfcab387
Timestamp: 1696725545 Timestamp [UCT]: 2023-10-08 00:39:05 Age [y:d:h:m:s]: 01:168:21:23:56
Block: 864805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381728 RingCT/type: yes/0
Extra: 01752b2e03ebef0aa43ce53a2c3151c5614b0993a115c9cc6ad4cdf246bfcab387021100000008faf35c9c000000000000000000

1 output(s) for total of 0.836646642000 dcy

stealth address amount amount idx
00: a4bf23cbcb5b244b81de4162294ea7be4f9ae1046f516f4b2d0b48957fffc383 0.836646642000 1319325 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 864815, "vin": [ { "gen": { "height": 864805 } } ], "vout": [ { "amount": 836646642, "target": { "key": "a4bf23cbcb5b244b81de4162294ea7be4f9ae1046f516f4b2d0b48957fffc383" } } ], "extra": [ 1, 117, 43, 46, 3, 235, 239, 10, 164, 60, 229, 58, 44, 49, 81, 197, 97, 75, 9, 147, 161, 21, 201, 204, 106, 212, 205, 242, 70, 191, 202, 179, 135, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8