Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 300b33f90c7913993b319369f222e86bc7590e9c5e2d8e4f25753ae1306b149a

Tx prefix hash: 9cca005e21ebad8405d8813292abacb4f1c14cf0f0c312816a08fe829f1e78c9
Tx public key: c0487f98846e9c80e579a136a7822bc319644076b8c3bc46f32c04287aa3f3c5
Timestamp: 1700334423 Timestamp [UCT]: 2023-11-18 19:07:03 Age [y:d:h:m:s]: 01:149:05:34:43
Block: 894512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367842 RingCT/type: yes/0
Extra: 01c0487f98846e9c80e579a136a7822bc319644076b8c3bc46f32c04287aa3f3c50211000000024b8f5122000000000000000000

1 output(s) for total of 0.666976306000 dcy

stealth address amount amount idx
00: 2f1009abbca779edd9d4ef5e1ea7849e9e707ca6aed3097bad05f15ec5716229 0.666976306000 1350715 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": 894522, "vin": [ { "gen": { "height": 894512 } } ], "vout": [ { "amount": 666976306, "target": { "key": "2f1009abbca779edd9d4ef5e1ea7849e9e707ca6aed3097bad05f15ec5716229" } } ], "extra": [ 1, 192, 72, 127, 152, 132, 110, 156, 128, 229, 121, 161, 54, 167, 130, 43, 195, 25, 100, 64, 118, 184, 195, 188, 70, 243, 44, 4, 40, 122, 163, 243, 197, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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