Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46cfc55d333e099554e66bea531e19b38d0cfa8dca30a198e4518746df7f9da8

Tx prefix hash: d8483d5aea0536c54bf3e0089f3bf8ae6ff71ec7a55638f76772238f9cb890be
Tx public key: 0aabf53ce80985a0377f50cd683e192528ae9a3a953437c803d428e387e50b19
Timestamp: 1702645448 Timestamp [UCT]: 2023-12-15 13:04:08 Age [y:d:h:m:s]: 01:152:05:03:57
Block: 913671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369948 RingCT/type: yes/0
Extra: 010aabf53ce80985a0377f50cd683e192528ae9a3a953437c803d428e387e50b1902110000000b33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 582a420b54c06d409df70ab80f193e0e438223c30f3bf1bcc3d2ff307380e2d1 0.600000000000 1370947 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": 913681, "vin": [ { "gen": { "height": 913671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "582a420b54c06d409df70ab80f193e0e438223c30f3bf1bcc3d2ff307380e2d1" } } ], "extra": [ 1, 10, 171, 245, 60, 232, 9, 133, 160, 55, 127, 80, 205, 104, 62, 25, 37, 40, 174, 154, 58, 149, 52, 55, 200, 3, 212, 40, 227, 135, 229, 11, 25, 2, 17, 0, 0, 0, 11, 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