Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20e449b498667adf176f5aa2d59374c38685f8ed47cee48c50ea080e99b5bd40

Tx prefix hash: a0ae6e876a4eaed5896568bd2590c917abc547610625e3a93151e44de929b3f3
Tx public key: 898dbad2a5f605046ec84dd9e4ff0e9042a671482430f77e49c3b0848ccb275b
Timestamp: 1634761846 Timestamp [UCT]: 2021-10-20 20:30:46 Age [y:d:h:m:s]: 03:115:06:36:50
Block: 357000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 860371 RingCT/type: yes/0
Extra: 01898dbad2a5f605046ec84dd9e4ff0e9042a671482430f77e49c3b0848ccb275b0211000000033fc41461000000000000000000

1 output(s) for total of 40.282017666000 dcy

stealth address amount amount idx
00: 869ce00a595850b9ff068a282a4f4dabb5a55fa8bd24e0f1ae916675e3552ad7 40.282017666000 728142 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": 357010, "vin": [ { "gen": { "height": 357000 } } ], "vout": [ { "amount": 40282017666, "target": { "key": "869ce00a595850b9ff068a282a4f4dabb5a55fa8bd24e0f1ae916675e3552ad7" } } ], "extra": [ 1, 137, 141, 186, 210, 165, 246, 5, 4, 110, 200, 77, 217, 228, 255, 14, 144, 66, 166, 113, 72, 36, 48, 247, 126, 73, 195, 176, 132, 140, 203, 39, 91, 2, 17, 0, 0, 0, 3, 63, 196, 20, 97, 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