Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 908aa4543b129f1729bdc1a1f9fe64bdee42b5309bf4c0fa20543d8a2a15c67c

Tx prefix hash: 12c688e40fcf6ea9266a2a765071856d3a916445be5b8411080bb34a12268c6e
Tx public key: cbdf3f2168289063240a8d843b114c65cb345e27fd684e24a8f7147a89dd2616
Timestamp: 1673001935 Timestamp [UCT]: 2023-01-06 10:45:35 Age [y:d:h:m:s]: 02:140:05:25:00
Block: 668778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 621952 RingCT/type: yes/0
Extra: 01cbdf3f2168289063240a8d843b114c65cb345e27fd684e24a8f7147a89dd2616021100000006e6d27f9c000000000000000000

1 output(s) for total of 3.733024344000 dcy

stealth address amount amount idx
00: e43ebfb667e25cdbcb1fa33fb09455a1012aefd0296f6926aecfe9eee707a0b2 3.733024344000 1110045 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": 668788, "vin": [ { "gen": { "height": 668778 } } ], "vout": [ { "amount": 3733024344, "target": { "key": "e43ebfb667e25cdbcb1fa33fb09455a1012aefd0296f6926aecfe9eee707a0b2" } } ], "extra": [ 1, 203, 223, 63, 33, 104, 40, 144, 99, 36, 10, 141, 132, 59, 17, 76, 101, 203, 52, 94, 39, 253, 104, 78, 36, 168, 247, 20, 122, 137, 221, 38, 22, 2, 17, 0, 0, 0, 6, 230, 210, 127, 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