Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2742b40805b06e727d9c9e38b47b82b9f48ad215264226413a854650ad893976

Tx prefix hash: 95cff781386c2ef557ca99357ae24970509d7b430e2b0ac7d9cca2d964b12737
Tx public key: f0eafb07583c81a4598301904d24c17ec84c7965eae8d42c1275b992c2c83381
Timestamp: 1732868517 Timestamp [UCT]: 2024-11-29 08:21:57 Age [y:d:h:m:s]: 00:149:00:24:38
Block: 1164144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106324 RingCT/type: yes/0
Extra: 01f0eafb07583c81a4598301904d24c17ec84c7965eae8d42c1275b992c2c83381021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac8f51b71e6756a02b273b9d046ad1fb5b88d23c248818763b80594b419b68fa 0.600000000000 1649817 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": 1164154, "vin": [ { "gen": { "height": 1164144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac8f51b71e6756a02b273b9d046ad1fb5b88d23c248818763b80594b419b68fa" } } ], "extra": [ 1, 240, 234, 251, 7, 88, 60, 129, 164, 89, 131, 1, 144, 77, 36, 193, 126, 200, 76, 121, 101, 234, 232, 212, 44, 18, 117, 185, 146, 194, 200, 51, 129, 2, 17, 0, 0, 0, 3, 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