Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e918903113946e1ef85dee8f47da10163d75cbcd28aea90c22cc51f7d3cb88a5

Tx prefix hash: 26d06223e10d118111c7908e3f5b5849afba08a04574c1c07758671e688b7f52
Tx public key: e51dfd20a5954d1e73dd250bbb4154e58b563f62d63a3a766b9fdaf259de23f2
Timestamp: 1720026794 Timestamp [UCT]: 2024-07-03 17:13:14 Age [y:d:h:m:s]: 01:141:23:51:30
Block: 1057779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360019 RingCT/type: yes/0
Extra: 01e51dfd20a5954d1e73dd250bbb4154e58b563f62d63a3a766b9fdaf259de23f20211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aca3e450b0c0b0ad03279132f321865187840d6ee43b6fbe68d4529f91c5ca1 0.600000000000 1528220 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": 1057789, "vin": [ { "gen": { "height": 1057779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aca3e450b0c0b0ad03279132f321865187840d6ee43b6fbe68d4529f91c5ca1" } } ], "extra": [ 1, 229, 29, 253, 32, 165, 149, 77, 30, 115, 221, 37, 11, 187, 65, 84, 229, 139, 86, 63, 98, 214, 58, 58, 118, 107, 159, 218, 242, 89, 222, 35, 242, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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