Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec09b6246e703e49f5d6b43eaeb2c262dc529f4d3ee147b028e098952e474cd6

Tx prefix hash: 2f76499d8aa15654f8f0ffc08daab965d147bc9a7337c3dae861188273da479c
Tx public key: b2b32f1a75f671b6fbbbb413a0ab3a3ac3a8f60446813a344b569c449e7c9db1
Timestamp: 1744887838 Timestamp [UCT]: 2025-04-17 11:03:58 Age [y:d:h:m:s]: 00:210:21:48:28
Block: 1263376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148464 RingCT/type: yes/0
Extra: 01b2b32f1a75f671b6fbbbb413a0ab3a3ac3a8f60446813a344b569c449e7c9db1021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18d2f435d904bb698d1b2a66209a4dbba69837572dd1811929f39ed064d3652d 0.600000000000 1750567 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": 1263386, "vin": [ { "gen": { "height": 1263376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18d2f435d904bb698d1b2a66209a4dbba69837572dd1811929f39ed064d3652d" } } ], "extra": [ 1, 178, 179, 47, 26, 117, 246, 113, 182, 251, 187, 180, 19, 160, 171, 58, 58, 195, 168, 246, 4, 70, 129, 58, 52, 75, 86, 156, 68, 158, 124, 157, 177, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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