Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7784d32d7c2418a9da979393e1b870e735e1e1c16ad6ef28dfc9bd3354ed05fc

Tx prefix hash: a38eb70ac1c76190400e2e9a1fc5e0497011f53eaf87f6a83e4e68c3d8699231
Tx public key: d073956fb430fb4fd0cb90e0459c524cd2a79a9308547a88ff79bd5ced53edf7
Timestamp: 1718297645 Timestamp [UCT]: 2024-06-13 16:54:05 Age [y:d:h:m:s]: 00:224:07:57:06
Block: 1043441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160497 RingCT/type: yes/0
Extra: 01d073956fb430fb4fd0cb90e0459c524cd2a79a9308547a88ff79bd5ced53edf70211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 287cfd81ba86e9385f8c587db49f781e2746c265388c9ec7e94897039e26abd4 0.600000000000 1512594 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": 1043451, "vin": [ { "gen": { "height": 1043441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "287cfd81ba86e9385f8c587db49f781e2746c265388c9ec7e94897039e26abd4" } } ], "extra": [ 1, 208, 115, 149, 111, 180, 48, 251, 79, 208, 203, 144, 224, 69, 156, 82, 76, 210, 167, 154, 147, 8, 84, 122, 136, 255, 121, 189, 92, 237, 83, 237, 247, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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