Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6946d4171327b76bd8f1bedefd34d7542d47b04c96bfc144272ca78c8a711f9

Tx prefix hash: cebe9638afe5bc8b4de4add85f1c72357301ac714d6e3e0c75992ab274525b05
Tx public key: a00cd047440a9b950cb8ee0a2ee93a14f3a10e69881c6836a2b03db0c78625f6
Timestamp: 1729747951 Timestamp [UCT]: 2024-10-24 05:32:31 Age [y:d:h:m:s]: 00:165:09:39:09
Block: 1138339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118011 RingCT/type: yes/0
Extra: 01a00cd047440a9b950cb8ee0a2ee93a14f3a10e69881c6836a2b03db0c78625f60211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 016c38f081758900fc7b8dfc4143ddf95e910dc021ae08c09b0439fe5edb78cd 0.600000000000 1621980 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": 1138349, "vin": [ { "gen": { "height": 1138339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "016c38f081758900fc7b8dfc4143ddf95e910dc021ae08c09b0439fe5edb78cd" } } ], "extra": [ 1, 160, 12, 208, 71, 68, 10, 155, 149, 12, 184, 238, 10, 46, 233, 58, 20, 243, 161, 14, 105, 136, 28, 104, 54, 162, 176, 61, 176, 199, 134, 37, 246, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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