Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 905d2bba48e3045ac35a4b12ba4065567ed660654366f5827dc8203d72520aa6

Tx prefix hash: 33cd0b450d50b9602582909c9b9447b7faca9de4067ffbfad0773e697e3757a0
Tx public key: 44def84695a4e85796b983a8c362b9f89207f71b894cb63f323b99caf733019d
Timestamp: 1716011154 Timestamp [UCT]: 2024-05-18 05:45:54 Age [y:d:h:m:s]: 00:126:00:00:07
Block: 1024484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90256 RingCT/type: yes/0
Extra: 0144def84695a4e85796b983a8c362b9f89207f71b894cb63f323b99caf733019d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84f259e332c535a55dd75dbc7472f4a47a7f4f0f9f70f7f23a88b4d94aa672be 0.600000000000 1490271 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": 1024494, "vin": [ { "gen": { "height": 1024484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84f259e332c535a55dd75dbc7472f4a47a7f4f0f9f70f7f23a88b4d94aa672be" } } ], "extra": [ 1, 68, 222, 248, 70, 149, 164, 232, 87, 150, 185, 131, 168, 195, 98, 185, 248, 146, 7, 247, 27, 137, 76, 182, 63, 50, 59, 153, 202, 247, 51, 1, 157, 2, 17, 0, 0, 0, 1, 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