Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e05660297f4339135b1401deffdc889e8d1979c5cddcd02d0f70d53503826ae8

Tx prefix hash: 83c948e4080b84ca7188b927c9bc80becfe5b14d3128f804a7339a7ae4c2743c
Tx public key: c5d805c01527c8ab83eeb3beff92aac83efa6d844423c2184796466e3f829e18
Timestamp: 1702225567 Timestamp [UCT]: 2023-12-10 16:26:07 Age [y:d:h:m:s]: 01:119:02:52:42
Block: 910191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346270 RingCT/type: yes/0
Extra: 01c5d805c01527c8ab83eeb3beff92aac83efa6d844423c2184796466e3f829e1802110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a60b9fb042e299c8fa0b26f2e60669bce9a10300893d41f01c4de24c6dfa216b 0.600000000000 1367336 of 15

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": 910201, "vin": [ { "gen": { "height": 910191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a60b9fb042e299c8fa0b26f2e60669bce9a10300893d41f01c4de24c6dfa216b" } } ], "extra": [ 1, 197, 216, 5, 192, 21, 39, 200, 171, 131, 238, 179, 190, 255, 146, 170, 200, 62, 250, 109, 132, 68, 35, 194, 24, 71, 150, 70, 110, 63, 130, 158, 24, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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