Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d16ad50de40ff91107717b9cab5bdd4261ebcc1cd11b208d1a75753f4aa82ff5

Tx prefix hash: 8b42faf5907e736f5948148ae318d674f3e4f4b1a2ff8bb3f934111de4640880
Tx public key: 7c9e8ac5c79f184e68e9ea2966f267db32417a71604d01b813d690f1517a6c71
Timestamp: 1649290008 Timestamp [UCT]: 2022-04-07 00:06:48 Age [y:d:h:m:s]: 03:024:15:54:02
Block: 474756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 798065 RingCT/type: yes/0
Extra: 017c9e8ac5c79f184e68e9ea2966f267db32417a71604d01b813d690f1517a6c710211000000024da16a3a000000000000000000

1 output(s) for total of 16.403500414000 dcy

stealth address amount amount idx
00: ae5c7f1c8c67d3ed15707e9ea8a05f71863153f67ea4bba0af4396bb46bb0b9e 16.403500414000 894863 of 0

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": 474766, "vin": [ { "gen": { "height": 474756 } } ], "vout": [ { "amount": 16403500414, "target": { "key": "ae5c7f1c8c67d3ed15707e9ea8a05f71863153f67ea4bba0af4396bb46bb0b9e" } } ], "extra": [ 1, 124, 158, 138, 197, 199, 159, 24, 78, 104, 233, 234, 41, 102, 242, 103, 219, 50, 65, 122, 113, 96, 77, 1, 184, 19, 214, 144, 241, 81, 122, 108, 113, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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