Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa357b3eefdc22d95d81195f5e9f646b35033c5dfbdd9cb6495ec91fa547a17f

Tx prefix hash: 5cc52d9e0f17180e931d244025fe70bd5bb3a48b5b25499ab35363090ffcc716
Tx public key: 5098d26739e0e68d11f8a3f863a9bfc2a1fa707fd46bbd34be33e65a156c55ed
Timestamp: 1728789472 Timestamp [UCT]: 2024-10-13 03:17:52 Age [y:d:h:m:s]: 01:027:16:29:19
Block: 1130426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278161 RingCT/type: yes/0
Extra: 015098d26739e0e68d11f8a3f863a9bfc2a1fa707fd46bbd34be33e65a156c55ed021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f90e3d25df51fb76faab9607c50749c00647ebde8a2002e1ab82b998ab05294e 0.600000000000 1613303 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": 1130436, "vin": [ { "gen": { "height": 1130426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f90e3d25df51fb76faab9607c50749c00647ebde8a2002e1ab82b998ab05294e" } } ], "extra": [ 1, 80, 152, 210, 103, 57, 224, 230, 141, 17, 248, 163, 248, 99, 169, 191, 194, 161, 250, 112, 127, 212, 107, 189, 52, 190, 51, 230, 90, 21, 108, 85, 237, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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