Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be9f28431d5305e2a7cf2786b3acceb140b2a01853f15acea9991c73a6c17f39

Tx prefix hash: 2f43a05ba7a2d7b1ef69d5c4638cf787312f3ab08602b9759b15d9ff45deba7c
Tx public key: 26edf75a618087a0fbdfdcabcbf66c4a605baa49ffc56969a74e9d6acf685c5f
Timestamp: 1705623417 Timestamp [UCT]: 2024-01-19 00:16:57 Age [y:d:h:m:s]: 01:294:16:05:05
Block: 938347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469417 RingCT/type: yes/0
Extra: 0126edf75a618087a0fbdfdcabcbf66c4a605baa49ffc56969a74e9d6acf685c5f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4d5cf696eb95149108e3f8f116409ec3175d57ce3299204a6a987434c21a401 0.600000000000 1396417 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": 938357, "vin": [ { "gen": { "height": 938347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4d5cf696eb95149108e3f8f116409ec3175d57ce3299204a6a987434c21a401" } } ], "extra": [ 1, 38, 237, 247, 90, 97, 128, 135, 160, 251, 223, 220, 171, 203, 246, 108, 74, 96, 91, 170, 73, 255, 197, 105, 105, 167, 78, 157, 106, 207, 104, 92, 95, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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