Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27d0b0996b9c2a3c14a79581ee0296bce3bff5b20603c9e9ecbd36f99e352b81

Tx prefix hash: 08f641ca63d35355a03f986cfd7779b4abaf1784a0a7eaa49e01fcd40a2de056
Tx public key: 200bc39323e3de35ae1cc8335d349b44182aa83cef9fa67b8b576494dcb1d769
Timestamp: 1705498173 Timestamp [UCT]: 2024-01-17 13:29:33 Age [y:d:h:m:s]: 01:320:07:59:05
Block: 937311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487795 RingCT/type: yes/0
Extra: 01200bc39323e3de35ae1cc8335d349b44182aa83cef9fa67b8b576494dcb1d7690211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef3fdd5e9a50d8c1ffd7b68a378407e20293149787cc5df413f19a63e1e94963 0.600000000000 1395361 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": 937321, "vin": [ { "gen": { "height": 937311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef3fdd5e9a50d8c1ffd7b68a378407e20293149787cc5df413f19a63e1e94963" } } ], "extra": [ 1, 32, 11, 195, 147, 35, 227, 222, 53, 174, 28, 200, 51, 93, 52, 155, 68, 24, 42, 168, 60, 239, 159, 166, 123, 139, 87, 100, 148, 220, 177, 215, 105, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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