Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de389972cf6c9447a1665dd31b82e4cec5b9cd08a5e6dd039f50042eb098d9c4

Tx prefix hash: 23ee1f1933dd554620209462e4a311d22f680766efe0a1b0889505d4c06636ca
Tx public key: a8dd576dc3ef5fd0ea2019fdd945d6548a9c754118e8e165775c1fb6d4300a4f
Timestamp: 1713303051 Timestamp [UCT]: 2024-04-16 21:30:51 Age [y:d:h:m:s]: 01:202:00:29:44
Block: 1002017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403045 RingCT/type: yes/0
Extra: 01a8dd576dc3ef5fd0ea2019fdd945d6548a9c754118e8e165775c1fb6d4300a4f02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3070299615216fd4583144d90809bfa3b4d47b8d4f582cee33e44a242aed2bf7 0.600000000000 1462531 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": 1002027, "vin": [ { "gen": { "height": 1002017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3070299615216fd4583144d90809bfa3b4d47b8d4f582cee33e44a242aed2bf7" } } ], "extra": [ 1, 168, 221, 87, 109, 195, 239, 95, 208, 234, 32, 25, 253, 217, 69, 214, 84, 138, 156, 117, 65, 24, 232, 225, 101, 119, 92, 31, 182, 212, 48, 10, 79, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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