Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87862ad583a56635f15e075663db34539a10209ee5a34b2659709fa0f5b1599e

Tx prefix hash: 906851fa62749f4c95794f8ed263f1f3f9bf9e36e4329e3903e590ea6a8c283d
Tx public key: 1640a464251f7a0bc2b5a737aa1be67fa6bb6decc021c3146dbce1ebad36489f
Timestamp: 1724745740 Timestamp [UCT]: 2024-08-27 08:02:20 Age [y:d:h:m:s]: 00:218:19:51:33
Block: 1096888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156256 RingCT/type: yes/0
Extra: 011640a464251f7a0bc2b5a737aa1be67fa6bb6decc021c3146dbce1ebad36489f02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 850993b741ce49ff5cec1b0e94fafda67a3a579a1aa4bae506b92a9a974a08ea 0.600000000000 1572097 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": 1096898, "vin": [ { "gen": { "height": 1096888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "850993b741ce49ff5cec1b0e94fafda67a3a579a1aa4bae506b92a9a974a08ea" } } ], "extra": [ 1, 22, 64, 164, 100, 37, 31, 122, 11, 194, 181, 167, 55, 170, 27, 230, 127, 166, 187, 109, 236, 192, 33, 195, 20, 109, 188, 225, 235, 173, 54, 72, 159, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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