Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acf0026f9b14ba179354b5b5ae28f39b6a3480a884db83e367fcd701342a2659

Tx prefix hash: 39a1c659bd081d18d8483073f3d4cf62bf3591bb14d671574b094f997d86d677
Tx public key: d78aa3caa18be9ad4d3d1f48226c2e3c71a99d1b7cf209df8d3fb4df0af067b4
Timestamp: 1765137022 Timestamp [UCT]: 2025-12-07 19:50:22 Age [y:d:h:m:s]: 00:031:23:52:44
Block: 1428629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22922 RingCT/type: yes/0
Extra: 01d78aa3caa18be9ad4d3d1f48226c2e3c71a99d1b7cf209df8d3fb4df0af067b40211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: badcac3e58443b78fb9613c3ce8c5124e879f2f967a5888a8ff9a0773f590bc1 0.600000000000 1917348 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": 1428639, "vin": [ { "gen": { "height": 1428629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "badcac3e58443b78fb9613c3ce8c5124e879f2f967a5888a8ff9a0773f590bc1" } } ], "extra": [ 1, 215, 138, 163, 202, 161, 139, 233, 173, 77, 61, 31, 72, 34, 108, 46, 60, 113, 169, 157, 27, 124, 242, 9, 223, 141, 63, 180, 223, 10, 240, 103, 180, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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