Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db7733eb02bfa59137785580776a428ad433cebe6021da9337370d6bd5b178a5

Tx prefix hash: 8cf5c082261c1a5e9f4ea02e602521709755c6af8132c29c15072a47c41dd638
Tx public key: 91d1b60d561c7feea1f0ee6b5aa44af2d03dae1bd116f96224efb49f39337af2
Timestamp: 1672588965 Timestamp [UCT]: 2023-01-01 16:02:45 Age [y:d:h:m:s]: 02:026:20:47:18
Block: 665359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540884 RingCT/type: yes/0
Extra: 0191d1b60d561c7feea1f0ee6b5aa44af2d03dae1bd116f96224efb49f39337af202110000000133af99f4000000000000000000

1 output(s) for total of 3.831681423000 dcy

stealth address amount amount idx
00: f1da254a11644c78f0fbfa186e8140ef3c1c741b7f9f9c864a7e6b6a34249e46 3.831681423000 1106398 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": 665369, "vin": [ { "gen": { "height": 665359 } } ], "vout": [ { "amount": 3831681423, "target": { "key": "f1da254a11644c78f0fbfa186e8140ef3c1c741b7f9f9c864a7e6b6a34249e46" } } ], "extra": [ 1, 145, 209, 182, 13, 86, 28, 127, 238, 161, 240, 238, 107, 90, 164, 74, 242, 208, 61, 174, 27, 209, 22, 249, 98, 36, 239, 180, 159, 57, 51, 122, 242, 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