Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2369132eb1b58612e3abff3d7138dbcc03697cfab7fefbf2c31b5032fefadaad

Tx prefix hash: 91d65799cec50d8823794a4e6d009c7ecced55e38f05af8f868581e4eb0fab48
Tx public key: d59a352af50337d12e331cdd792a8cac9e8e4ba5f902c8cf7f663d77f9dba8c9
Timestamp: 1725597483 Timestamp [UCT]: 2024-09-06 04:38:03 Age [y:d:h:m:s]: 00:170:06:05:19
Block: 1103964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121481 RingCT/type: yes/0
Extra: 01d59a352af50337d12e331cdd792a8cac9e8e4ba5f902c8cf7f663d77f9dba8c9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b90905dede2534bdb62faa846a56a804032eb4d5f927d04659a6e88d1758f0e0 0.600000000000 1580995 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": 1103974, "vin": [ { "gen": { "height": 1103964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b90905dede2534bdb62faa846a56a804032eb4d5f927d04659a6e88d1758f0e0" } } ], "extra": [ 1, 213, 154, 53, 42, 245, 3, 55, 209, 46, 51, 28, 221, 121, 42, 140, 172, 158, 142, 75, 165, 249, 2, 200, 207, 127, 102, 61, 119, 249, 219, 168, 201, 2, 17, 0, 0, 0, 4, 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