Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9a260c00a36b97a7972d0e936605cdd48f306b66ae8893e39e2c7ea7545236

Tx prefix hash: 8f9f692cca53a598edac82f81b200bed9a221f727e178fa60ee3fd8e93077f1a
Tx public key: ea444e7346dd55a6ba6099dd7e7576f102607d33cd74f5103d76334fce8a97c1
Timestamp: 1714872112 Timestamp [UCT]: 2024-05-05 01:21:52 Age [y:d:h:m:s]: 00:243:22:58:59
Block: 1015052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174612 RingCT/type: yes/0
Extra: 01ea444e7346dd55a6ba6099dd7e7576f102607d33cd74f5103d76334fce8a97c102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fba6e629c32a4e1b9f9fd0991cf09ddaf4c8e85829b665fa4f182e229915aa9 0.600000000000 1478311 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": 1015062, "vin": [ { "gen": { "height": 1015052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fba6e629c32a4e1b9f9fd0991cf09ddaf4c8e85829b665fa4f182e229915aa9" } } ], "extra": [ 1, 234, 68, 78, 115, 70, 221, 85, 166, 186, 96, 153, 221, 126, 117, 118, 241, 2, 96, 125, 51, 205, 116, 245, 16, 61, 118, 51, 79, 206, 138, 151, 193, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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