Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f83a690444a5879d9a2db321ce07d17505db52a05a321c3af028d2aaa57bbe

Tx prefix hash: b29d00d850f5f22f99e7a50edc1c006350266ac3b175a9b63f6cd40c51d84779
Tx public key: d3c68d533af695f57b5e02c07e4254ce1c0b20f448df6eef92e1302e4dea8904
Timestamp: 1726759003 Timestamp [UCT]: 2024-09-19 15:16:43 Age [y:d:h:m:s]: 00:245:09:16:45
Block: 1113590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175240 RingCT/type: yes/0
Extra: 01d3c68d533af695f57b5e02c07e4254ce1c0b20f448df6eef92e1302e4dea8904021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04bd5899c5f88cfa44ba7de026d966c4bf8f0841ccbf6f78a94836fbae9520a7 0.600000000000 1593317 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": 1113600, "vin": [ { "gen": { "height": 1113590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04bd5899c5f88cfa44ba7de026d966c4bf8f0841ccbf6f78a94836fbae9520a7" } } ], "extra": [ 1, 211, 198, 141, 83, 58, 246, 149, 245, 123, 94, 2, 192, 126, 66, 84, 206, 28, 11, 32, 244, 72, 223, 110, 239, 146, 225, 48, 46, 77, 234, 137, 4, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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