Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83444ad4eca5cc4e743443d0d20fc8b3a675c86df55e371aee41fe3a10335d22

Tx prefix hash: d46d7ed666eba9c98edfec97ac0ade6ec0390b6be57f41e3b4cb4d6bb707fa65
Tx public key: 84e2ae3e925f040347a9a2ac46efa80b66408bc50f6cfa9c5690607aeaaba5f8
Timestamp: 1702077404 Timestamp [UCT]: 2023-12-08 23:16:44 Age [y:d:h:m:s]: 01:347:21:16:19
Block: 908961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507510 RingCT/type: yes/0
Extra: 0184e2ae3e925f040347a9a2ac46efa80b66408bc50f6cfa9c5690607aeaaba5f8021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 012959279b0398dcbfc4ef42d79451c94d7a3ad523dbd3e44043f2a53bfb9429 0.600000000000 1366024 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": 908971, "vin": [ { "gen": { "height": 908961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "012959279b0398dcbfc4ef42d79451c94d7a3ad523dbd3e44043f2a53bfb9429" } } ], "extra": [ 1, 132, 226, 174, 62, 146, 95, 4, 3, 71, 169, 162, 172, 70, 239, 168, 11, 102, 64, 139, 197, 15, 108, 250, 156, 86, 144, 96, 122, 234, 171, 165, 248, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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