Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 992d7083ac28eab099ab185ceffdd3445f395b654f2032e58b4d37a09a9fc08b

Tx prefix hash: cea3382bb7c3dc14d1adde7eb71d57894fb99d7f8a88204663603c994a179ff8
Tx public key: 1fc5c8b1ed972869faafacb83a679e1a5c1cff18c18fe47dc38574f6ca1a5b6a
Timestamp: 1710397457 Timestamp [UCT]: 2024-03-14 06:24:17 Age [y:d:h:m:s]: 01:101:11:48:13
Block: 977962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333324 RingCT/type: yes/0
Extra: 011fc5c8b1ed972869faafacb83a679e1a5c1cff18c18fe47dc38574f6ca1a5b6a02110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 097c3a40955c6deceb4acd09a88cff1aaebcc8898aefe7824970114d583cf30c 0.600000000000 1437971 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": 977972, "vin": [ { "gen": { "height": 977962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "097c3a40955c6deceb4acd09a88cff1aaebcc8898aefe7824970114d583cf30c" } } ], "extra": [ 1, 31, 197, 200, 177, 237, 151, 40, 105, 250, 175, 172, 184, 58, 103, 158, 26, 92, 28, 255, 24, 193, 143, 228, 125, 195, 133, 116, 246, 202, 26, 91, 106, 2, 17, 0, 0, 0, 15, 0, 17, 5, 91, 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