Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb96c49f57fbc23dd9789fe5420d499f4aafe1af4c083fcc3fa5e80dfbbfd3b2

Tx prefix hash: 979217d9046ea8d1897dc8c665662f2fe505de2e3eee707f16cf1ec4a19e5691
Tx public key: e3664b1406247bfbb67f40640ae825428989ea30792eb93c346d3320c6d340c6
Timestamp: 1752087977 Timestamp [UCT]: 2025-07-09 19:06:17 Age [y:d:h:m:s]: 00:134:05:31:20
Block: 1322117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94470 RingCT/type: yes/0
Extra: 01e3664b1406247bfbb67f40640ae825428989ea30792eb93c346d3320c6d340c60211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed3fb207c4d7dde415c8c918a5c0b35b5bd29083ced6c5a3cfb0e3984e467e5 0.600000000000 1809830 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": 1322127, "vin": [ { "gen": { "height": 1322117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed3fb207c4d7dde415c8c918a5c0b35b5bd29083ced6c5a3cfb0e3984e467e5" } } ], "extra": [ 1, 227, 102, 75, 20, 6, 36, 123, 251, 182, 127, 64, 100, 10, 232, 37, 66, 137, 137, 234, 48, 121, 46, 185, 60, 52, 109, 51, 32, 198, 211, 64, 198, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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