Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a313b41dc93b62ab07bfa46a5392531c711f4beccd62c572515bb1089e1e2d82

Tx prefix hash: da68e65f00521957a98d9ad3bdf7a44a545d8f483f1c9f24a7d232069f2815a0
Tx public key: 65fc14057c87c889812b2737aba41d9e594d1af1eac7b76e3aa9f288c9495954
Timestamp: 1749136257 Timestamp [UCT]: 2025-06-05 15:10:57 Age [y:d:h:m:s]: 00:165:16:26:00
Block: 1298572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116087 RingCT/type: yes/0
Extra: 0165fc14057c87c889812b2737aba41d9e594d1af1eac7b76e3aa9f288c949595402110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbae1369b40ad057f95c8119a482f2a2df2ba7dcf9d8acbc8380845dfa3716a1 0.600000000000 1786101 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": 1298582, "vin": [ { "gen": { "height": 1298572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbae1369b40ad057f95c8119a482f2a2df2ba7dcf9d8acbc8380845dfa3716a1" } } ], "extra": [ 1, 101, 252, 20, 5, 124, 135, 200, 137, 129, 43, 39, 55, 171, 164, 29, 158, 89, 77, 26, 241, 234, 199, 183, 110, 58, 169, 242, 136, 201, 73, 89, 84, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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