Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4313f84d9943df22deea056b54d96882db874f9e6b28a1db0e0fe3e12d946654

Tx prefix hash: f3b20a2f831a45082e5a304565b898d2d7865d883c0ecf73ef108c2b75b96d50
Tx public key: da4396911044f94c095495f82871c796c356c9a13371a5fe6f749984f68c5572
Timestamp: 1730802499 Timestamp [UCT]: 2024-11-05 10:28:19 Age [y:d:h:m:s]: 00:022:22:14:43
Block: 1147029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16408 RingCT/type: yes/0
Extra: 01da4396911044f94c095495f82871c796c356c9a13371a5fe6f749984f68c55720211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 980a1d4022fdfb271bc813ec6b12dbd6c6db5aad2084cf042bc1e528e7f7750b 0.600000000000 1631722 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": 1147039, "vin": [ { "gen": { "height": 1147029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "980a1d4022fdfb271bc813ec6b12dbd6c6db5aad2084cf042bc1e528e7f7750b" } } ], "extra": [ 1, 218, 67, 150, 145, 16, 68, 249, 76, 9, 84, 149, 248, 40, 113, 199, 150, 195, 86, 201, 161, 51, 113, 165, 254, 111, 116, 153, 132, 246, 140, 85, 114, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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