Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c50f182d5012f710ebdfa0c92c510629bf1c5bd727f44c239a1c1a5e7838b79f

Tx prefix hash: 4070de6b97444f23c60134195c4f1abc58339cc7bc4dfad40c429ebed7c41629
Tx public key: b241405bf899a38fa32a9b0f6599f0d3e9a725ae10c94d83fa5e470bbd27255e
Timestamp: 1576923752 Timestamp [UCT]: 2019-12-21 10:22:32 Age [y:d:h:m:s]: 05:074:14:06:54
Block: 28769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202826 RingCT/type: yes/0
Extra: 01b241405bf899a38fa32a9b0f6599f0d3e9a725ae10c94d83fa5e470bbd27255e0211000000048a2ee0d9000000000000000000

1 output(s) for total of 492.807404464000 dcy

stealth address amount amount idx
00: 68440f67e8b117195349e6e409629a415b3fb841157f2d12fe0ef0b558d7a0f8 492.807404464000 47559 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": 28779, "vin": [ { "gen": { "height": 28769 } } ], "vout": [ { "amount": 492807404464, "target": { "key": "68440f67e8b117195349e6e409629a415b3fb841157f2d12fe0ef0b558d7a0f8" } } ], "extra": [ 1, 178, 65, 64, 91, 248, 153, 163, 143, 163, 42, 155, 15, 101, 153, 240, 211, 233, 167, 37, 174, 16, 201, 77, 131, 250, 94, 71, 11, 189, 39, 37, 94, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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