Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a35f8655c4504a0e9417a3cadca6b98f60634f62e1d7e123c789a1f07cfd1922

Tx prefix hash: c01918e04000f3c905ce9a17749e13fcbd3ee21d9ec17fe1efa8fa600d3f03d2
Tx public key: 6cd7a2a221b9c354612f9a3f7e2fd74249479bbf5d8be4d22d7b887a5d5910bf
Timestamp: 1734631865 Timestamp [UCT]: 2024-12-19 18:11:05 Age [y:d:h:m:s]: 00:103:05:17:36
Block: 1178766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73533 RingCT/type: yes/0
Extra: 016cd7a2a221b9c354612f9a3f7e2fd74249479bbf5d8be4d22d7b887a5d5910bf021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e901a734d2ab31090d7b34699a630dd0fdc45dd2cec79d912c3843375763a8ae 0.600000000000 1665155 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": 1178776, "vin": [ { "gen": { "height": 1178766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e901a734d2ab31090d7b34699a630dd0fdc45dd2cec79d912c3843375763a8ae" } } ], "extra": [ 1, 108, 215, 162, 162, 33, 185, 195, 84, 97, 47, 154, 63, 126, 47, 215, 66, 73, 71, 155, 191, 93, 139, 228, 210, 45, 123, 136, 122, 93, 89, 16, 191, 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