Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dfed1c5285ad5520f251d8194b3c44c5e49496c5e395569c66943f1b4597b29

Tx prefix hash: 5d36729af9294bfe3f20b3dc742a3f546b461c13d4bc61ea40964ff4e299ccd4
Tx public key: 6b2664db2d76567b9d807bb48928197a3583ca5b595e5b747923155910a3b9f1
Timestamp: 1725623730 Timestamp [UCT]: 2024-09-06 11:55:30 Age [y:d:h:m:s]: 00:211:21:45:59
Block: 1104184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151284 RingCT/type: yes/0
Extra: 016b2664db2d76567b9d807bb48928197a3583ca5b595e5b747923155910a3b9f1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0e0bef8355fc2bb9150823d6da8652c19255cd23a0f43d4ef6b2fefc41bf811 0.600000000000 1581263 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": 1104194, "vin": [ { "gen": { "height": 1104184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0e0bef8355fc2bb9150823d6da8652c19255cd23a0f43d4ef6b2fefc41bf811" } } ], "extra": [ 1, 107, 38, 100, 219, 45, 118, 86, 123, 157, 128, 123, 180, 137, 40, 25, 122, 53, 131, 202, 91, 89, 94, 91, 116, 121, 35, 21, 89, 16, 163, 185, 241, 2, 17, 0, 0, 0, 3, 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