Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43b2f225d70e1185adf2939a43a25cebaf21cbe0d5fd1187639cc95799595fa8

Tx prefix hash: cfa6ff35d6de7ad7ea6408137b9a67f664d123437a273804c6fdc0d1179087af
Tx public key: 4f4fbe9c87d6f2fd1711dd79d4c39b2fa1b44150f70974e788b2360a83741da1
Timestamp: 1710688281 Timestamp [UCT]: 2024-03-17 15:11:21 Age [y:d:h:m:s]: 01:020:22:24:12
Block: 980377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275913 RingCT/type: yes/0
Extra: 014f4fbe9c87d6f2fd1711dd79d4c39b2fa1b44150f70974e788b2360a83741da10211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d4bd00b7effbf15cc2d1edf90c9486c5668a1fafc2a555e46fb937a73582283 0.600000000000 1440442 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": 980387, "vin": [ { "gen": { "height": 980377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d4bd00b7effbf15cc2d1edf90c9486c5668a1fafc2a555e46fb937a73582283" } } ], "extra": [ 1, 79, 79, 190, 156, 135, 214, 242, 253, 23, 17, 221, 121, 212, 195, 155, 47, 161, 180, 65, 80, 247, 9, 116, 231, 136, 178, 54, 10, 131, 116, 29, 161, 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