Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98a52bf7ab4e1d464414341c52ff0a68f06b35a68985da2f0d2ccac30a21b9af

Tx prefix hash: 50a869e4a6020d29800fc5e2a4e2673802169eb768c98dee827fbf85773d42af
Tx public key: d2f9ad0576a00853e80ff89d7435a6eb28617bcc60bd3fb0dc1a1b3b86781011
Timestamp: 1710986127 Timestamp [UCT]: 2024-03-21 01:55:27 Age [y:d:h:m:s]: 00:358:07:38:19
Block: 982840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256195 RingCT/type: yes/0
Extra: 01d2f9ad0576a00853e80ff89d7435a6eb28617bcc60bd3fb0dc1a1b3b867810110211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d03cbe8cd83707beb54ef794e137ee27f3cac2ed44249fda4c4aa391efaf4f2 0.600000000000 1442953 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": 982850, "vin": [ { "gen": { "height": 982840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d03cbe8cd83707beb54ef794e137ee27f3cac2ed44249fda4c4aa391efaf4f2" } } ], "extra": [ 1, 210, 249, 173, 5, 118, 160, 8, 83, 232, 15, 248, 157, 116, 53, 166, 235, 40, 97, 123, 204, 96, 189, 63, 176, 220, 26, 27, 59, 134, 120, 16, 17, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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