Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41ae76fd287c9b2cc3f22d2605987b137c02a7167e53ccd77e2b6ffcf3cd2d29

Tx prefix hash: 55701df59080a7aa2f26cfa6a3440547d418d76aa465843f964784e6600388ee
Tx public key: 10096828056087df5ffc18c56894e8121b9de310c3625fa680a51c73c90a9ea2
Timestamp: 1714352012 Timestamp [UCT]: 2024-04-29 00:53:32 Age [y:d:h:m:s]: 00:355:05:15:46
Block: 1010724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253936 RingCT/type: yes/0
Extra: 0110096828056087df5ffc18c56894e8121b9de310c3625fa680a51c73c90a9ea202110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e65a8d2dfdaec56b9d4a0b59f0ca93873d4a3877a9ffe5f5c77c09d2473f60a4 0.600000000000 1472762 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": 1010734, "vin": [ { "gen": { "height": 1010724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e65a8d2dfdaec56b9d4a0b59f0ca93873d4a3877a9ffe5f5c77c09d2473f60a4" } } ], "extra": [ 1, 16, 9, 104, 40, 5, 96, 135, 223, 95, 252, 24, 197, 104, 148, 232, 18, 27, 157, 227, 16, 195, 98, 95, 166, 128, 165, 28, 115, 201, 10, 158, 162, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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