Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c5d90bbc102f085f81353b98353c8dacdc88201b7372319ab703a5d55f86462

Tx prefix hash: 9fd4674ad42f1d12deaf62136d37dc8a2d331db7c1d71b2ee6b00b65fe70ff7b
Tx public key: 70e99770fbb538e5f2cfc4c45c963600c9914711fd2507dc3428195539b4fd94
Timestamp: 1728517909 Timestamp [UCT]: 2024-10-09 23:51:49 Age [y:d:h:m:s]: 00:183:03:53:57
Block: 1128170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130702 RingCT/type: yes/0
Extra: 0170e99770fbb538e5f2cfc4c45c963600c9914711fd2507dc3428195539b4fd94021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e08326f2bc2895fb1028d5a1f30f0fe7d6c87178f7e0e03d681f788b0f004ba 0.600000000000 1610987 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": 1128180, "vin": [ { "gen": { "height": 1128170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e08326f2bc2895fb1028d5a1f30f0fe7d6c87178f7e0e03d681f788b0f004ba" } } ], "extra": [ 1, 112, 233, 151, 112, 251, 181, 56, 229, 242, 207, 196, 196, 92, 150, 54, 0, 201, 145, 71, 17, 253, 37, 7, 220, 52, 40, 25, 85, 57, 180, 253, 148, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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