Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8392be7a8fb4a0184591df159924f8a26a063ef2c9f6124febe5859cbb7ce5f0

Tx prefix hash: 2f800a4b1589d1e1c4324c04feca63324957225d8a3bb6fe69dc0a7afcf52dee
Tx public key: 7f1747bf9341c4714cc55e5c7d0afc4e23ef19737ac59204763f94e17bccb753
Timestamp: 1727422612 Timestamp [UCT]: 2024-09-27 07:36:52 Age [y:d:h:m:s]: 01:041:05:29:57
Block: 1119104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287847 RingCT/type: yes/0
Extra: 017f1747bf9341c4714cc55e5c7d0afc4e23ef19737ac59204763f94e17bccb75302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04110fd7a65ba93a33a404e2c0782c173173477954cbc6eb56651f5dae9a5c18 0.600000000000 1600537 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": 1119114, "vin": [ { "gen": { "height": 1119104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04110fd7a65ba93a33a404e2c0782c173173477954cbc6eb56651f5dae9a5c18" } } ], "extra": [ 1, 127, 23, 71, 191, 147, 65, 196, 113, 76, 197, 94, 92, 125, 10, 252, 78, 35, 239, 25, 115, 122, 197, 146, 4, 118, 63, 148, 225, 123, 204, 183, 83, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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