Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0adf30be905ab49a25c8c773d8ef2b37274a5c8958e6c12a54a59ef645e85b32

Tx prefix hash: 3eacd5f8182af5056e5d4c0b8fece5fea7b0c745ae9f0b5384b1960b738b5b98
Tx public key: 33f8e2540230db763d2b5386e5c0c1ce5657ef8cccdfb632afa1ff671e70a2ea
Timestamp: 1582035026 Timestamp [UCT]: 2020-02-18 14:10:26 Age [y:d:h:m:s]: 05:118:15:03:11
Block: 67453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1237868 RingCT/type: yes/0
Extra: 0133f8e2540230db763d2b5386e5c0c1ce5657ef8cccdfb632afa1ff671e70a2ea0211000000020aca7173000000000000000000

1 output(s) for total of 366.860553815000 dcy

stealth address amount amount idx
00: 2aa7dfe7d091b78e2db1524ef8e4f54af51247f4c7e22a6c615fedf6cd1e20f8 366.860553815000 124304 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": 67463, "vin": [ { "gen": { "height": 67453 } } ], "vout": [ { "amount": 366860553815, "target": { "key": "2aa7dfe7d091b78e2db1524ef8e4f54af51247f4c7e22a6c615fedf6cd1e20f8" } } ], "extra": [ 1, 51, 248, 226, 84, 2, 48, 219, 118, 61, 43, 83, 134, 229, 192, 193, 206, 86, 87, 239, 140, 204, 223, 182, 50, 175, 161, 255, 103, 30, 112, 162, 234, 2, 17, 0, 0, 0, 2, 10, 202, 113, 115, 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