Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d903c72d921bda8f7e0ca83e8346791785e7323112740faa0a78b196c629d817

Tx prefix hash: 0a6a12387bfde295d99af971a4724a7f77a27c5133ae36ddf932e293be180b1e
Tx public key: 67c9075e67a9c3db627bb6970880b9292f299ab36084b234aa1f1dd5840937eb
Timestamp: 1672800282 Timestamp [UCT]: 2023-01-04 02:44:42 Age [y:d:h:m:s]: 02:054:11:26:02
Block: 667118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560585 RingCT/type: yes/0
Extra: 0167c9075e67a9c3db627bb6970880b9292f299ab36084b234aa1f1dd5840937eb02110000000bfaf35c9c000000000000000000

1 output(s) for total of 3.780603165000 dcy

stealth address amount amount idx
00: df029bb17516f2aed8f2f8794310cf717f440e764ff172c44ff60368d04a55aa 3.780603165000 1108283 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": 667128, "vin": [ { "gen": { "height": 667118 } } ], "vout": [ { "amount": 3780603165, "target": { "key": "df029bb17516f2aed8f2f8794310cf717f440e764ff172c44ff60368d04a55aa" } } ], "extra": [ 1, 103, 201, 7, 94, 103, 169, 195, 219, 98, 123, 182, 151, 8, 128, 185, 41, 47, 41, 154, 179, 96, 132, 178, 52, 170, 31, 29, 213, 132, 9, 55, 235, 2, 17, 0, 0, 0, 11, 250, 243, 92, 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