Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f906389f02a0e30dab1280f6f59c7e9105a552cefa901f07bca60f95d12ff7e9

Tx prefix hash: 050d6a2636b0f90a5171ffebf3948cd8bfcc3e7c65a1e3b7eadb51ace6d799e4
Tx public key: 0bafdf4162c6127afabc9e3deedf14b32ab2c1ebd902d820e567b33f8873c517
Timestamp: 1758256544 Timestamp [UCT]: 2025-09-19 04:35:44 Age [y:d:h:m:s]: 00:111:06:07:31
Block: 1371616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79660 RingCT/type: yes/0
Extra: 010bafdf4162c6127afabc9e3deedf14b32ab2c1ebd902d820e567b33f8873c517021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f70eea974f425ee0f06bda17ce567db140fa95e56a43b76c10afa5a0816ccbc 0.600000000000 1859693 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": 1371626, "vin": [ { "gen": { "height": 1371616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f70eea974f425ee0f06bda17ce567db140fa95e56a43b76c10afa5a0816ccbc" } } ], "extra": [ 1, 11, 175, 223, 65, 98, 198, 18, 122, 250, 188, 158, 61, 238, 223, 20, 179, 42, 178, 193, 235, 217, 2, 216, 32, 229, 103, 179, 63, 136, 115, 197, 23, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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