Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 412f34dd8e7d854db288ea223450bccee20bd558eb6a4efd0f7d875295939cea

Tx prefix hash: a63aaf654de18f2b94616e4e2a47f8e728a58f0ddf0dba8c0183d9ca9209262d
Tx public key: 9e3430d63f5146353cd1b7de07d4d931426b7e41a22d4600adfe36cfcffdfcd2
Timestamp: 1748616410 Timestamp [UCT]: 2025-05-30 14:46:50 Age [y:d:h:m:s]: 00:164:10:28:03
Block: 1294262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115194 RingCT/type: yes/0
Extra: 019e3430d63f5146353cd1b7de07d4d931426b7e41a22d4600adfe36cfcffdfcd2021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f32fcda4fbf9ea412b8037f686af926c435a3525b208fca39412d3ec9fa0dea 0.600000000000 1781757 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": 1294272, "vin": [ { "gen": { "height": 1294262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f32fcda4fbf9ea412b8037f686af926c435a3525b208fca39412d3ec9fa0dea" } } ], "extra": [ 1, 158, 52, 48, 214, 63, 81, 70, 53, 60, 209, 183, 222, 7, 212, 217, 49, 66, 107, 126, 65, 162, 45, 70, 0, 173, 254, 54, 207, 207, 253, 252, 210, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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