Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72c37bffbe5b1812e2cab056bf9304539271934c86bc11a176de97445a8c222a

Tx prefix hash: 047b0d16714dfcd5ba3e95722ce56109d918cd2b80f189425768c11dc0fd5725
Tx public key: 41cc6aad88f807d33b68fca07d7a2c46feb8296b4e200bbb79ea20c475066b1f
Timestamp: 1723529974 Timestamp [UCT]: 2024-08-13 06:19:34 Age [y:d:h:m:s]: 00:292:14:52:05
Block: 1086817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209061 RingCT/type: yes/0
Extra: 0141cc6aad88f807d33b68fca07d7a2c46feb8296b4e200bbb79ea20c475066b1f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d4d0b5fb7013f1b1845ccf458e87788db50e658f4032b5c33b4602339b7478 0.600000000000 1561416 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": 1086827, "vin": [ { "gen": { "height": 1086817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d4d0b5fb7013f1b1845ccf458e87788db50e658f4032b5c33b4602339b7478" } } ], "extra": [ 1, 65, 204, 106, 173, 136, 248, 7, 211, 59, 104, 252, 160, 125, 122, 44, 70, 254, 184, 41, 107, 78, 32, 11, 187, 121, 234, 32, 196, 117, 6, 107, 31, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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