Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 980311fd48815b1ed11b4031836dfa988d222f2dc8e76efaa0260d7f3acffbc0

Tx prefix hash: 55b9163fd16249edff1620b7d185ecadd70e3cc87d94879c5dfba1f5819d7e3f
Tx public key: 6ac2d6dc2d4e732b87e92b5d316ae8a33fbf0cf9c867de3d40f17a82522d8dc7
Timestamp: 1729003295 Timestamp [UCT]: 2024-10-15 14:41:35 Age [y:d:h:m:s]: 00:007:15:50:07
Block: 1132208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5444 RingCT/type: yes/0
Extra: 016ac2d6dc2d4e732b87e92b5d316ae8a33fbf0cf9c867de3d40f17a82522d8dc702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e5a5430dd96a915743fe0a79d906c92ab2e9789fdacdcca1f7129beee271819 0.600000000000 1615121 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": 1132218, "vin": [ { "gen": { "height": 1132208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e5a5430dd96a915743fe0a79d906c92ab2e9789fdacdcca1f7129beee271819" } } ], "extra": [ 1, 106, 194, 214, 220, 45, 78, 115, 43, 135, 233, 43, 93, 49, 106, 232, 163, 63, 191, 12, 249, 200, 103, 222, 61, 64, 241, 122, 130, 82, 45, 141, 199, 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