Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3bd55b23726b1d64e408a9ea8aa718e0fc9fec441cbdabe6c4ec5debbbe0edf

Tx prefix hash: fd78eafd5eace271aab1ed06b247b9e06cf083006efaa12d87e9663674ab515c
Tx public key: ae4993fd6325c2efe313c803905531e431ecca5a0909945ee1b6c3e084220a7c
Timestamp: 1710386060 Timestamp [UCT]: 2024-03-14 03:14:20 Age [y:d:h:m:s]: 00:346:13:43:55
Block: 977867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247763 RingCT/type: yes/0
Extra: 01ae4993fd6325c2efe313c803905531e431ecca5a0909945ee1b6c3e084220a7c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 167140d1e9f62419d55aa644eac50a9769c4e7694024b0b9c17383d0966777ce 0.600000000000 1437874 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": 977877, "vin": [ { "gen": { "height": 977867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "167140d1e9f62419d55aa644eac50a9769c4e7694024b0b9c17383d0966777ce" } } ], "extra": [ 1, 174, 73, 147, 253, 99, 37, 194, 239, 227, 19, 200, 3, 144, 85, 49, 228, 49, 236, 202, 90, 9, 9, 148, 94, 225, 182, 195, 224, 132, 34, 10, 124, 2, 17, 0, 0, 0, 3, 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