Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37eabb96f7f13acaddfff363ac20c26271dfd2a957c791dec213b2eef885f68b

Tx prefix hash: 78fd0f79232bd07a2bb64530fae9554f9e7ea771843145bd329efd7201632825
Tx public key: c80bdc0f057b289eaa52ca2bda84c8fe8516b20025f1c3cb1d0bcbb6e3f07bf7
Timestamp: 1657120549 Timestamp [UCT]: 2022-07-06 15:15:49 Age [y:d:h:m:s]: 02:176:03:40:13
Block: 537948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647247 RingCT/type: yes/0
Extra: 01c80bdc0f057b289eaa52ca2bda84c8fe8516b20025f1c3cb1d0bcbb6e3f07bf70211000000072e6b1fd5000000000000000000

1 output(s) for total of 10.128732769000 dcy

stealth address amount amount idx
00: bd6ce3853fdefd8f8e0f2e5eabe970b9d5a3aee1e776a401d0f843ec0423a572 10.128732769000 967889 of 0

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": 537958, "vin": [ { "gen": { "height": 537948 } } ], "vout": [ { "amount": 10128732769, "target": { "key": "bd6ce3853fdefd8f8e0f2e5eabe970b9d5a3aee1e776a401d0f843ec0423a572" } } ], "extra": [ 1, 200, 11, 220, 15, 5, 123, 40, 158, 170, 82, 202, 43, 218, 132, 200, 254, 133, 22, 178, 0, 37, 241, 195, 203, 29, 11, 203, 182, 227, 240, 123, 247, 2, 17, 0, 0, 0, 7, 46, 107, 31, 213, 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