Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78c261150564fdd22759e6263feb6b097e950e131e0e4043591b65f271d3d2e8

Tx prefix hash: 3de9660196c6bb7b672c4ab4238aaf4f55b6540262349d5edc04bae2b4acc3e9
Tx public key: c6202bed3af6581d7ba44da9143bca02cb38c6edfd634cb16fb23de10fe13dcb
Timestamp: 1698385311 Timestamp [UCT]: 2023-10-27 05:41:51 Age [y:d:h:m:s]: 01:156:19:44:12
Block: 878577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373066 RingCT/type: yes/0
Extra: 01c6202bed3af6581d7ba44da9143bca02cb38c6edfd634cb16fb23de10fe13dcb02110000000233af99f4000000000000000000

1 output(s) for total of 0.753198938000 dcy

stealth address amount amount idx
00: d9201ab360d188ceb21484d0f4cf98151b23d87b74ce2501957d4a60c99b587d 0.753198938000 1334029 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": 878587, "vin": [ { "gen": { "height": 878577 } } ], "vout": [ { "amount": 753198938, "target": { "key": "d9201ab360d188ceb21484d0f4cf98151b23d87b74ce2501957d4a60c99b587d" } } ], "extra": [ 1, 198, 32, 43, 237, 58, 246, 88, 29, 123, 164, 77, 169, 20, 59, 202, 2, 203, 56, 198, 237, 253, 99, 76, 177, 111, 178, 61, 225, 15, 225, 61, 203, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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