Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36c20b8e7c1acd898b833c7e7e4d0203dea9dffb89caa06636b4a3f4e4931bc6

Tx prefix hash: 714f91345a037178621384128104677d77f979d79ed58a73fab9012dcabd108f
Tx public key: ec5daccb9ae1351679ae5eea83777e4d99e9985fb65bc0293d97a7d82ff4bfe0
Timestamp: 1722109157 Timestamp [UCT]: 2024-07-27 19:39:17 Age [y:d:h:m:s]: 01:103:12:05:52
Block: 1075046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332460 RingCT/type: yes/0
Extra: 01ec5daccb9ae1351679ae5eea83777e4d99e9985fb65bc0293d97a7d82ff4bfe0021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dd45a9225ed160a8d6ddc50d8d83fbca93d89f6ec54461a0adbd26c124019e1 0.600000000000 1547567 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": 1075056, "vin": [ { "gen": { "height": 1075046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dd45a9225ed160a8d6ddc50d8d83fbca93d89f6ec54461a0adbd26c124019e1" } } ], "extra": [ 1, 236, 93, 172, 203, 154, 225, 53, 22, 121, 174, 94, 234, 131, 119, 126, 77, 153, 233, 152, 95, 182, 91, 192, 41, 61, 151, 167, 216, 47, 244, 191, 224, 2, 17, 0, 0, 0, 6, 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