Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 158a70d0adee5b8fbaf14c2fb57891055ec05f44d603580c9d778c2448efd36a

Tx prefix hash: fc4bb636da4e70522504295079652b326fdcd87bee2dfa950ab80aa1c0fd482f
Tx public key: 067e1182044181305946a00233f3ebd4fb79f939398828e23c8db88c3e01e4c0
Timestamp: 1745877644 Timestamp [UCT]: 2025-04-28 22:00:44 Age [y:d:h:m:s]: 00:196:01:21:54
Block: 1271582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137821 RingCT/type: yes/0
Extra: 01067e1182044181305946a00233f3ebd4fb79f939398828e23c8db88c3e01e4c00211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 658d3da307f4f5fda2fef643a9fb4b1191a6edb85d18e9395994656e63a8b227 0.600000000000 1758847 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": 1271592, "vin": [ { "gen": { "height": 1271582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "658d3da307f4f5fda2fef643a9fb4b1191a6edb85d18e9395994656e63a8b227" } } ], "extra": [ 1, 6, 126, 17, 130, 4, 65, 129, 48, 89, 70, 160, 2, 51, 243, 235, 212, 251, 121, 249, 57, 57, 136, 40, 226, 60, 141, 184, 140, 62, 1, 228, 192, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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