Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e1472c1e8243b865adc65c26b072e88e1abc536a9a0a15be6803d7ec6dc4f37

Tx prefix hash: 251c2f072087f068dd570200ccfa86d9b7d932d0007f947c4fbd47959d500361
Tx public key: 73ffb0cc9a1dd4685b373307e15f5e8f053f29573449ed6c2f958ad52c280788
Timestamp: 1636229304 Timestamp [UCT]: 2021-11-06 20:08:24 Age [y:d:h:m:s]: 03:127:08:50:33
Block: 368794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 869384 RingCT/type: yes/0
Extra: 0173ffb0cc9a1dd4685b373307e15f5e8f053f29573449ed6c2f958ad52c280788021100000001328bb496000000000000000000

1 output(s) for total of 36.815676093000 dcy

stealth address amount amount idx
00: 7e59d103ae964c742ddb16cc6d02352fd31dbc293135ea3428dc824b581ebe7f 36.815676093000 747946 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": 368804, "vin": [ { "gen": { "height": 368794 } } ], "vout": [ { "amount": 36815676093, "target": { "key": "7e59d103ae964c742ddb16cc6d02352fd31dbc293135ea3428dc824b581ebe7f" } } ], "extra": [ 1, 115, 255, 176, 204, 154, 29, 212, 104, 91, 55, 51, 7, 225, 95, 94, 143, 5, 63, 41, 87, 52, 73, 237, 108, 47, 149, 138, 213, 44, 40, 7, 136, 2, 17, 0, 0, 0, 1, 50, 139, 180, 150, 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