Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f7ba98ee4a400e72e8046d65543fff5776f6d817772359ca0db7d8e3d5bd9b2

Tx prefix hash: 02ab6728e622de24abaa8a051608b772a3c3d6dbabb550fa7566eeba51dee0dd
Tx public key: 083936fd8b05d4e6bf3be88d27dd89e0b06c45a89ca8c549b1f081c58a02f05e
Timestamp: 1751980190 Timestamp [UCT]: 2025-07-08 13:09:50 Age [y:d:h:m:s]: 00:126:22:00:56
Block: 1321334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89139 RingCT/type: yes/0
Extra: 01083936fd8b05d4e6bf3be88d27dd89e0b06c45a89ca8c549b1f081c58a02f05e021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bb3feebe17c4f1cc8e11db08d483500cc483e180f09a8c28f6fe773298a374e 0.600000000000 1809039 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": 1321344, "vin": [ { "gen": { "height": 1321334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb3feebe17c4f1cc8e11db08d483500cc483e180f09a8c28f6fe773298a374e" } } ], "extra": [ 1, 8, 57, 54, 253, 139, 5, 212, 230, 191, 59, 232, 141, 39, 221, 137, 224, 176, 108, 69, 168, 156, 168, 197, 73, 177, 240, 129, 197, 138, 2, 240, 94, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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