Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fbdcbe5fc16aade156df6e690d668a0ea003d6598a08bcaa3b9b6c4733961dc

Tx prefix hash: 45d2332c8ac4a2995f2343e5be0e3f8cc08810ea407f81aa2d7ba74c180924f5
Tx public key: f699ff99a08c88b796005f9071799cb6fb49194320ab3596b1f5eb10ec966c6a
Timestamp: 1745613007 Timestamp [UCT]: 2025-04-25 20:30:07 Age [y:d:h:m:s]: 00:253:19:30:59
Block: 1269387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179194 RingCT/type: yes/0
Extra: 01f699ff99a08c88b796005f9071799cb6fb49194320ab3596b1f5eb10ec966c6a021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be6c295651dea7a619073e62e03f92db2629e7da807598c41c85ffdd11adce0a 0.600000000000 1756622 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": 1269397, "vin": [ { "gen": { "height": 1269387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be6c295651dea7a619073e62e03f92db2629e7da807598c41c85ffdd11adce0a" } } ], "extra": [ 1, 246, 153, 255, 153, 160, 140, 136, 183, 150, 0, 95, 144, 113, 121, 156, 182, 251, 73, 25, 67, 32, 171, 53, 150, 177, 245, 235, 16, 236, 150, 108, 106, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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