Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d02799921d553211508cd2b1e55929505d777471951dd4d3b0ac7e09db1d50d

Tx prefix hash: d9917e9c4f74d583e014626927f573ee07b7990b36ae5a14b0c8732590a09bff
Tx public key: f8e7d97f1e5209307db38e8ad638707e2f4281e2c770a459fa8d26f66074ec46
Timestamp: 1701200673 Timestamp [UCT]: 2023-11-28 19:44:33 Age [y:d:h:m:s]: 01:159:14:34:57
Block: 901701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375248 RingCT/type: yes/0
Extra: 01f8e7d97f1e5209307db38e8ad638707e2f4281e2c770a459fa8d26f66074ec46021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.631379176000 dcy

stealth address amount amount idx
00: 8b0d0879ddd635d722adb414da8b4d9c1f651b131ef8c365e7fab43774615b6a 0.631379176000 1358284 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": 901711, "vin": [ { "gen": { "height": 901701 } } ], "vout": [ { "amount": 631379176, "target": { "key": "8b0d0879ddd635d722adb414da8b4d9c1f651b131ef8c365e7fab43774615b6a" } } ], "extra": [ 1, 248, 231, 217, 127, 30, 82, 9, 48, 125, 179, 142, 138, 214, 56, 112, 126, 47, 66, 129, 226, 199, 112, 164, 89, 250, 141, 38, 246, 96, 116, 236, 70, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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