Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb71870b76dc4fead1bd32fc11c94bfabd12e7e494f88a23980b676b93974f4d

Tx prefix hash: 89d999ed7883e7eac9c2b9946e4310d9e39617f2a69f3c324374390e83af6707
Tx public key: 574b7a60af878ddb78aa2ec96a0f2be6a8718d9f5a55614db0184680ea7851e4
Timestamp: 1704175326 Timestamp [UCT]: 2024-01-02 06:02:06 Age [y:d:h:m:s]: 01:094:02:57:22
Block: 926355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328386 RingCT/type: yes/0
Extra: 01574b7a60af878ddb78aa2ec96a0f2be6a8718d9f5a55614db0184680ea7851e402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cd05dc045df3dfa971e445135cbaad2d43fa24e2366d944d62170e1583b48d8 0.600000000000 1384137 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": 926365, "vin": [ { "gen": { "height": 926355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cd05dc045df3dfa971e445135cbaad2d43fa24e2366d944d62170e1583b48d8" } } ], "extra": [ 1, 87, 75, 122, 96, 175, 135, 141, 219, 120, 170, 46, 201, 106, 15, 43, 230, 168, 113, 141, 159, 90, 85, 97, 77, 176, 24, 70, 128, 234, 120, 81, 228, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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