Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 463c112b127218782c6b229d5d90ea31a5ed32ca3497b8f61e8e8551aef50f51

Tx prefix hash: 68930731736b26d083718027d1325bf4c7f8521852ae03a32a610b09e038b907
Tx public key: 6fbca3d1e5aa4854384d0b303a86773d68c4f0f015acb55160cea10f42fa0502
Timestamp: 1703805315 Timestamp [UCT]: 2023-12-28 23:15:15 Age [y:d:h:m:s]: 01:107:01:38:27
Block: 923291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337659 RingCT/type: yes/0
Extra: 016fbca3d1e5aa4854384d0b303a86773d68c4f0f015acb55160cea10f42fa050202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11dd058a877c2027d564861f94020e1dfa56c7d024f2d5a29dac59d39cd063de 0.600000000000 1381019 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": 923301, "vin": [ { "gen": { "height": 923291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11dd058a877c2027d564861f94020e1dfa56c7d024f2d5a29dac59d39cd063de" } } ], "extra": [ 1, 111, 188, 163, 209, 229, 170, 72, 84, 56, 77, 11, 48, 58, 134, 119, 61, 104, 196, 240, 240, 21, 172, 181, 81, 96, 206, 161, 15, 66, 250, 5, 2, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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