Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c36f5d8b11860c00f38b630634a7cfb5c4c9281a2f283b411cf16989376443ff

Tx prefix hash: 6093865f02760aeb8a7fd30c7f7fa17c792ad96a323d6455897cc2a89592226d
Tx public key: 8d9776fc963b617719df702910962958f5416b33264cf2bbeb07339cbf9ae5b2
Timestamp: 1694334157 Timestamp [UCT]: 2023-09-10 08:22:37 Age [y:d:h:m:s]: 01:121:04:45:33
Block: 844950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347948 RingCT/type: yes/0
Extra: 018d9776fc963b617719df702910962958f5416b33264cf2bbeb07339cbf9ae5b2021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.973486557000 dcy

stealth address amount amount idx
00: 6d3894b48c5443ff8e363335f271de9478fa35b998f6d0b35d4971f3592ae69d 0.973486557000 1298292 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": 844960, "vin": [ { "gen": { "height": 844950 } } ], "vout": [ { "amount": 973486557, "target": { "key": "6d3894b48c5443ff8e363335f271de9478fa35b998f6d0b35d4971f3592ae69d" } } ], "extra": [ 1, 141, 151, 118, 252, 150, 59, 97, 119, 25, 223, 112, 41, 16, 150, 41, 88, 245, 65, 107, 51, 38, 76, 242, 187, 235, 7, 51, 156, 191, 154, 229, 178, 2, 17, 0, 0, 0, 4, 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