Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fa204b9905c5db715418eea3b685284944c08598ac7d28d045137d2bbd493b3

Tx prefix hash: 11e475e26ae9c45e28d64a89a39278845097bc35471673d3bac1a65d8131628d
Tx public key: 47f7cdb586a2602d68402022fb5b022c5926cd7cd6c1bc3de3073df99a7aff0e
Timestamp: 1712897319 Timestamp [UCT]: 2024-04-12 04:48:39 Age [y:d:h:m:s]: 00:317:09:02:37
Block: 998644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226891 RingCT/type: yes/0
Extra: 0147f7cdb586a2602d68402022fb5b022c5926cd7cd6c1bc3de3073df99a7aff0e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5ce6127e0f4676560a7b11b539c65d6d97420c99c7c8f31c3fb3bbdd7d2d40 0.600000000000 1459096 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": 998654, "vin": [ { "gen": { "height": 998644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5ce6127e0f4676560a7b11b539c65d6d97420c99c7c8f31c3fb3bbdd7d2d40" } } ], "extra": [ 1, 71, 247, 205, 181, 134, 162, 96, 45, 104, 64, 32, 34, 251, 91, 2, 44, 89, 38, 205, 124, 214, 193, 188, 61, 227, 7, 61, 249, 154, 122, 255, 14, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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