Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497450b6f59715bb2eac49b3ee7d3f3ce2880911b78aad475ed4ca056c59a7b2

Tx prefix hash: e308cc09cded14b4ddd87fceee990cb35d886b48f76afb4f6b3860fae4a6a24a
Tx public key: 9986e4f9507434869217005d68c8fee0cf5275eff4dbfa27e6c652c9785450d8
Timestamp: 1701218890 Timestamp [UCT]: 2023-11-29 00:48:10 Age [y:d:h:m:s]: 01:337:15:43:35
Block: 901840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500211 RingCT/type: yes/0
Extra: 019986e4f9507434869217005d68c8fee0cf5275eff4dbfa27e6c652c9785450d802110000000833af99f4000000000000000000

1 output(s) for total of 0.630709960000 dcy

stealth address amount amount idx
00: eaa3958f3edd2f28f1b2bb2fec7a549156dc97f4dc491c9fd885327e0feb06fb 0.630709960000 1358433 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": 901850, "vin": [ { "gen": { "height": 901840 } } ], "vout": [ { "amount": 630709960, "target": { "key": "eaa3958f3edd2f28f1b2bb2fec7a549156dc97f4dc491c9fd885327e0feb06fb" } } ], "extra": [ 1, 153, 134, 228, 249, 80, 116, 52, 134, 146, 23, 0, 93, 104, 200, 254, 224, 207, 82, 117, 239, 244, 219, 250, 39, 230, 198, 82, 201, 120, 84, 80, 216, 2, 17, 0, 0, 0, 8, 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