Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e37b4045c9cb67967c69f3cd121a070b7f02f7108dffe425b8f6fad378f3669

Tx prefix hash: 399ccd450d8cdf61cc679321d268a64def62518770eeadcc97513be6033fb7b0
Tx public key: 7d849490e89307d0b0b09f33634f867883c42176cb9c86af9bb247a17c8b8b94
Timestamp: 1726550680 Timestamp [UCT]: 2024-09-17 05:24:40 Age [y:d:h:m:s]: 00:158:22:31:29
Block: 1111859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113382 RingCT/type: yes/0
Extra: 017d849490e89307d0b0b09f33634f867883c42176cb9c86af9bb247a17c8b8b9402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95dcfb0fd3b571fb437150cbc871d7c97238962938e6e5ecf3332f88f1689f02 0.600000000000 1590970 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": 1111869, "vin": [ { "gen": { "height": 1111859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95dcfb0fd3b571fb437150cbc871d7c97238962938e6e5ecf3332f88f1689f02" } } ], "extra": [ 1, 125, 132, 148, 144, 232, 147, 7, 208, 176, 176, 159, 51, 99, 79, 134, 120, 131, 196, 33, 118, 203, 156, 134, 175, 155, 178, 71, 161, 124, 139, 139, 148, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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