Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96cdeffbb34b5bb6f365a999d27f6d95fd76448dc3f3e38ac449c700105859a3

Tx prefix hash: 2e9fd6c80eed4180218d490fd47a4eeded3f9f2a6cb8db5bd88bab978166f283
Tx public key: 3f6b5a611b30e9800d9c6caa087cfa41acb0ecba435975a17d8e3eb453d802ea
Timestamp: 1577316233 Timestamp [UCT]: 2019-12-25 23:23:53 Age [y:d:h:m:s]: 04:316:23:40:56
Block: 31713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115678 RingCT/type: yes/0
Extra: 013f6b5a611b30e9800d9c6caa087cfa41acb0ecba435975a17d8e3eb453d802ea0211000000094943cd9f000000000000000000

1 output(s) for total of 481.861830487000 dcy

stealth address amount amount idx
00: 71598a0b8bded35071470f40b78585278464c8c31d0d23bbe9ad9fc1204ca6e7 481.861830487000 52568 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": 31723, "vin": [ { "gen": { "height": 31713 } } ], "vout": [ { "amount": 481861830487, "target": { "key": "71598a0b8bded35071470f40b78585278464c8c31d0d23bbe9ad9fc1204ca6e7" } } ], "extra": [ 1, 63, 107, 90, 97, 27, 48, 233, 128, 13, 156, 108, 170, 8, 124, 250, 65, 172, 176, 236, 186, 67, 89, 117, 161, 125, 142, 62, 180, 83, 216, 2, 234, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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