Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28a786ccb9a59106e65d38b1b747fa3cf93c97240cb26afd4feae9f8b58fe603

Tx prefix hash: adcacdd5e88c87f790c60ac57c6687e9ccb1e9207ae8dce31e730fd6ba9b556a
Tx public key: 088111c0bd9669f2884e2f5e747a301c81efd35f1c74a0cbdd41c0630e6e8d95
Timestamp: 1720182893 Timestamp [UCT]: 2024-07-05 12:34:53 Age [y:d:h:m:s]: 00:275:03:58:57
Block: 1059066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196602 RingCT/type: yes/0
Extra: 01088111c0bd9669f2884e2f5e747a301c81efd35f1c74a0cbdd41c0630e6e8d950211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64e897d4e4daa1ee0911252fa96f0df4829e1a534f7af4e0dc35dafb7cc73113 0.600000000000 1529527 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": 1059076, "vin": [ { "gen": { "height": 1059066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64e897d4e4daa1ee0911252fa96f0df4829e1a534f7af4e0dc35dafb7cc73113" } } ], "extra": [ 1, 8, 129, 17, 192, 189, 150, 105, 242, 136, 78, 47, 94, 116, 122, 48, 28, 129, 239, 211, 95, 28, 116, 160, 203, 221, 65, 192, 99, 14, 110, 141, 149, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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