Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a12af2e24981befca0f830394e2ba86913609459c26112bb74d3f70ea70a85f

Tx prefix hash: 80d8ad37b42ead6f6f8f9db1c2942d69ba3fac569bcc419529c87dbccf5e8929
Tx public key: dd7641fbf3cd4aa63bfc9be45c619ffa079274a04aa7f3e46f03070e1b102552
Timestamp: 1738077210 Timestamp [UCT]: 2025-01-28 15:13:30 Age [y:d:h:m:s]: 00:323:00:49:25
Block: 1207019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228660 RingCT/type: yes/0
Extra: 01dd7641fbf3cd4aa63bfc9be45c619ffa079274a04aa7f3e46f03070e1b102552021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a72bac33bd23ea0e99454ed253c15415a5e0e7cb1fa2594276c23910edef7d5 0.600000000000 1693740 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": 1207029, "vin": [ { "gen": { "height": 1207019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a72bac33bd23ea0e99454ed253c15415a5e0e7cb1fa2594276c23910edef7d5" } } ], "extra": [ 1, 221, 118, 65, 251, 243, 205, 74, 166, 59, 252, 155, 228, 92, 97, 159, 250, 7, 146, 116, 160, 74, 167, 243, 228, 111, 3, 7, 14, 27, 16, 37, 82, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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