Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d835d1191b8454692829557e37e03296973d08bcbfe63e7e41606dbc8eb2a805

Tx prefix hash: 63aca54b9cccbce1ff1fb4b77e040eb48bdb07c3684c8bcbb1f22bd34b96f807
Tx public key: 401f8a69676bd6d665831a6090354c21d0ea5f0b13b3dc6ad19b48a2d0e58ed3
Timestamp: 1728843711 Timestamp [UCT]: 2024-10-13 18:21:51 Age [y:d:h:m:s]: 00:102:16:50:24
Block: 1130874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73366 RingCT/type: yes/0
Extra: 01401f8a69676bd6d665831a6090354c21d0ea5f0b13b3dc6ad19b48a2d0e58ed3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3718071db63c38c1f95ca1913a6d51679bf39ea92e812d78256c36808977bd89 0.600000000000 1613755 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": 1130884, "vin": [ { "gen": { "height": 1130874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3718071db63c38c1f95ca1913a6d51679bf39ea92e812d78256c36808977bd89" } } ], "extra": [ 1, 64, 31, 138, 105, 103, 107, 214, 214, 101, 131, 26, 96, 144, 53, 76, 33, 208, 234, 95, 11, 19, 179, 220, 106, 209, 155, 72, 162, 208, 229, 142, 211, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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