Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 277535b68d6c9a92109af5b1ea4972886c288f6739e7e0c0331f180b00d628ed

Tx prefix hash: be687f0db0d77904fece80dca998beb42f4c66009e4f1c856fa0bd31b6106dc6
Tx public key: 74beb021cb4d7344c67a0832e97d67d2abb806cc19e7f58cb604356861a55684
Timestamp: 1703751765 Timestamp [UCT]: 2023-12-28 08:22:45 Age [y:d:h:m:s]: 02:036:03:33:12
Block: 922845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545462 RingCT/type: yes/0
Extra: 0174beb021cb4d7344c67a0832e97d67d2abb806cc19e7f58cb604356861a55684021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44fc2b7ea9b176d2df6fff53c60a27fc3fbf60af565f7afbec0f57f37d414e4e 0.600000000000 1380551 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": 922855, "vin": [ { "gen": { "height": 922845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44fc2b7ea9b176d2df6fff53c60a27fc3fbf60af565f7afbec0f57f37d414e4e" } } ], "extra": [ 1, 116, 190, 176, 33, 203, 77, 115, 68, 198, 122, 8, 50, 233, 125, 103, 210, 171, 184, 6, 204, 25, 231, 245, 140, 182, 4, 53, 104, 97, 165, 86, 132, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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