Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f11f2cc79eb215b63b8bf8a6d078a68dd3bba217b18e28e859ad086f4aa08bb2

Tx prefix hash: 534f56739535dc73de2f93e33058d815eb256bf8d707a22da7aa0a69e2cd5bbb
Tx public key: b589725e9ec3e0550e365175eb2f1e49e9277a1f45c253d604c218c76f0dfae1
Timestamp: 1760966858 Timestamp [UCT]: 2025-10-20 13:27:38 Age [y:d:h:m:s]: 00:098:12:09:43
Block: 1394095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70326 RingCT/type: yes/0
Extra: 01b589725e9ec3e0550e365175eb2f1e49e9277a1f45c253d604c218c76f0dfae1021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d17cbb5dc072a56315cbdce016d166b884517b5053a0bce454546bade1891b1 0.600000000000 1882362 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": 1394105, "vin": [ { "gen": { "height": 1394095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d17cbb5dc072a56315cbdce016d166b884517b5053a0bce454546bade1891b1" } } ], "extra": [ 1, 181, 137, 114, 94, 158, 195, 224, 85, 14, 54, 81, 117, 235, 47, 30, 73, 233, 39, 122, 31, 69, 194, 83, 214, 4, 194, 24, 199, 111, 13, 250, 225, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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