Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06319ffa26ca123670da8cb294d1570c12d052273b924d878101c3497e14e501

Tx prefix hash: 33aedd8db58ce759a6ebf99cde6f141e901c4f1a129df771d70600b9009fe06e
Tx public key: ea27e341689aa43bb9ad0bd73af5a830e998c319c12d3c10c5f9a98a423da253
Timestamp: 1734320479 Timestamp [UCT]: 2024-12-16 03:41:19 Age [y:d:h:m:s]: 00:104:10:30:02
Block: 1176186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74406 RingCT/type: yes/0
Extra: 01ea27e341689aa43bb9ad0bd73af5a830e998c319c12d3c10c5f9a98a423da25302110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89b05da89c7e6748ca6f40bedd3bd2b4a836358a81f76f84a7dc9b34a34cea49 0.600000000000 1662517 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": 1176196, "vin": [ { "gen": { "height": 1176186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89b05da89c7e6748ca6f40bedd3bd2b4a836358a81f76f84a7dc9b34a34cea49" } } ], "extra": [ 1, 234, 39, 227, 65, 104, 154, 164, 59, 185, 173, 11, 215, 58, 245, 168, 48, 233, 152, 195, 25, 193, 45, 60, 16, 197, 249, 169, 138, 66, 61, 162, 83, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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