Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57c6b48b90d119cb33221870bb4caa9fd1295461292262779a8b4f470c0c9597

Tx prefix hash: 4dbbe0a930d9d80214c333cfe7174951a3647e779fac0ffe08250401941ad1df
Tx public key: 46f152c4f023ecc7bb91e6e5de94af8e15a47c7bfc30a9b6b941e37651a9c6cf
Timestamp: 1722736783 Timestamp [UCT]: 2024-08-04 01:59:43 Age [y:d:h:m:s]: 00:159:16:42:59
Block: 1080246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114249 RingCT/type: yes/0
Extra: 0146f152c4f023ecc7bb91e6e5de94af8e15a47c7bfc30a9b6b941e37651a9c6cf021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8cadfa21420247591c4b4e0409051e0ab7296c2d83d26b96a44c2161cc06375 0.600000000000 1553531 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": 1080256, "vin": [ { "gen": { "height": 1080246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8cadfa21420247591c4b4e0409051e0ab7296c2d83d26b96a44c2161cc06375" } } ], "extra": [ 1, 70, 241, 82, 196, 240, 35, 236, 199, 187, 145, 230, 229, 222, 148, 175, 142, 21, 164, 124, 123, 252, 48, 169, 182, 185, 65, 227, 118, 81, 169, 198, 207, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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