Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c37523479e765aa8400d9e4c8efd9bad02b3af242f9d857084f9c11c03e5bb67

Tx prefix hash: 0e1e103566ad560e316797d37f2563198611fbfcdbbd0b3f1b209b91a6121d94
Tx public key: 588f44dfa5c919582f65311e4887d823b4f2ab7288b575f70e226a6c16b350e3
Timestamp: 1702698715 Timestamp [UCT]: 2023-12-16 03:51:55 Age [y:d:h:m:s]: 01:122:01:09:08
Block: 914119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348360 RingCT/type: yes/0
Extra: 01588f44dfa5c919582f65311e4887d823b4f2ab7288b575f70e226a6c16b350e302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aec27d3aff94284fec23015fe7ce91f8e493a3e0d21723495a51eddae9f9616b 0.600000000000 1371403 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": 914129, "vin": [ { "gen": { "height": 914119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aec27d3aff94284fec23015fe7ce91f8e493a3e0d21723495a51eddae9f9616b" } } ], "extra": [ 1, 88, 143, 68, 223, 165, 201, 25, 88, 47, 101, 49, 30, 72, 135, 216, 35, 180, 242, 171, 114, 136, 181, 117, 247, 14, 34, 106, 108, 22, 179, 80, 227, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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